The Mainframe Product must generate audit records when successful/unsuccessful attempts to modify security objects occur.

Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The Mainframe Product must generate audit records when successful/unsuccessful attempts to modify security objects occur.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-68201	SRG-APP-000496-MFP-000121	SV-82691r1_rule		Medium

Description
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter).

STIG	Date
Mainframe Product Security Requirements Guide	2019-12-12

Details

Check Text ( C-68763r1_chk )
Examine installation and configuration settings. Verify that the Mainframe Product identifies all security object; writes to SMF and/or uses an external security manager to generate audit records when successful/unsuccessful attempts to modify security objects. If it does not, this is a finding.

Fix Text (F-74317r1_fix)
Configure the Mainframe Product to write to SMF and/or provide audit SAF to call when successful/unsuccessful attempts to modify security objects occur.